This page describes the steps required for registering a new developer for the CCNet project. If you are interested in becoming a committer on the CCNet project, please contact the CCNet project administrators; bestowing of commit rights is generally contingent on having a number of contributed patches accepted, participation in the CCNet community, and a demonstrated knowledge of the codebase and of how to do test-driven development.

Registration Process

1. If you have not already done so, please review and send an email expressing your acceptance of the CCNet Contributor License Agreement to the CCNet developers list .
2. Send your sourceforge user id to the project administrator to be added to the sourceforge project and given svn commit rights.
3. Create a new account on Confluence and send your user id to the project administrator to receive write access to the wiki.
4. Create a new account on Jira and send your user id to the project administrator to receive issue editing access.
5. Register for the CCNet user and CCNet developers mailing lists.
6. Register for the CCNet checkins checkins mailing list using your sourceforge email address (ie. username@users.sourceforge.net) – you may want to do this using the 'No email' option. This will allow svn diff emails from your sourceforge account to be sent out to the list. If you don't do this, then the group will block the message and no one will see your commit. If you want to receive commit log emails, then subscribe to this list (this is optional).
7. Check out the latest source from the svn repository using TortoiseSvn
8. Add your name to the Project Team page.

Starting development

Once you have completed registration, you are ready to start working on the code. Here is how to get started.

1. Please review the Developer Guidelines. If you have any questions about the coding standards, please ask on the CCNet developers mailing list. In general, code formatting follows the default ReSharper guidelines. If you don't already have it, please download and install ReSharper. If you can't afford a license, we may be able to arrange one for you. Please ensure that the code style box is green for all modified code files.
2. If you are looking for something to work on, take a look through Jira and pick up an issue.
3. If you are ready to commit a change, please ensure that you follow the defined Commit Process